home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
tex-k-archive.gz
/
tex-k-archive
/
000470_kb@cs.umb.edu_Wed Apr 6 10:35:36 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-11
|
3KB
Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA04408
(5.65c/IDA-1.4.4 for <tex-k-exp@cs.umb.edu>); Wed, 6 Apr 1994 14:35:37 -0400
Received: by terminus.cs.umb.edu id AA11176
(5.65c/IDA-1.4.4 for tex-k); Wed, 6 Apr 1994 14:35:36 -0400
Date: Wed, 6 Apr 1994 14:35:36 -0400
From: "K. Berry" <kb@cs.umb.edu>
Message-Id: <199404061835.AA11176@terminus.cs.umb.edu>
To: tex-k@cs.umb.edu
Subject: converting a driver to use kpathsea
Neal asked me about converting a driver to use kpathsea.
I hope he doesn't mind my posting this reply, for the benefit of all you
hordes of others out there wanting to do that :-)
I'm psyching myself up to convert my 'eps' driver to use kpathsea.
:-)
1) read pre/postamble
2) give me bitmaps for glyphs
kpathsea doesn't do either of these things :-(
Its purpose in life is to give you back a filename (that is, a string)
which you can then fopen.
Pretty minimal, huh, for all the hub-bub and bugs? And yet just doing
this has been a sufficient challenge that I haven't gotten into
libraries for the file reading yet.
(Well, I did write libraries to read PK/GF/TFM files -- they're in the
fontutils distribution on prep. But they have nothing to do with kpathsea.)
Where do you suggest I look for examples? I have glanced at dvipsk,
All three simultaneously :-)
Seriously, they all have their uses.
dvips is probably the closest to your application (resident.c and
search.c have most of the relevant stuff.)
xdvi's dataflow is somewhat easier (for me) to comprehend than
dvips'. Relevant files here are dvi_init.c, font-open.c (which is all my
code), and some initializations in xdvi.c. But xdvi the program is
probably the worst-written of the three.
dvi2xx is annoying because it's just one file. But the kpathsea changes
are actually smaller and simpler for it than either of the others. Look
for `kpse_'.
But the real place to look is probably the .h files in kpathsea itself.
I try hard to document all the external functions. Of course there's no
grand overview :-( The interfaces are still changing, as I continually
discover stupid ideas I had ... and so anything lacking is almost
certainly a result of my muddled thinking -- so please, I'm happy to
receive suggestions about the source code (as well as the user features
which no one has been shy to give :-).
tex-file.h and tex-glyph.h are the highest-level routines, and are
probably the ones you want to start with (and use).
K